SRWX Edge caches your site’s static files — HTML, CSS, images, scripts — on 14 edge servers worldwide. An edge server is a node close to the visitor: someone in Frankfurt gets files from Frankfurt, someone in Tokyo — from Tokyo. Pages load 3–5× faster and your hosting load drops. Setup takes ten minutes.
Three common cases where an edge cache pays for itself on day one.
A WordPress or static site with an audience across the country and abroad. Once the edge is in front, pages open in 0.4–0.8 s instead of 2–3 s. Core Web Vitals turn green and conversion climbs.
A React/Vue app or Docusaurus docs: the build weighs 20–50 MB. Ship it with one command from CI. The edge serves every asset — bundles never touch your server, and a new version goes live right after deploy.
Manuals, price lists, client videos — anything shared by link. The edge answers range requests, so video seeks instantly without downloading the whole file. Your hosting stops being the bottleneck.
Three steps — and 14 servers serve your static files instead of one.
The srwx deploy command uploads a directory to the edge and replicates it to every region. Or automate it from GitHub Actions — on every release.
A single CNAME record (a DNS alias) — and files are live on your domain. A Let’s Encrypt certificate is issued and renewed automatically; there’s nothing to configure.
Shipped a new version — srwx purge purges the cache across all 14 regions in 5 seconds. No more “wait two hours until it propagates”.
# install the CLI and log in
curl -sSL https://cdn.srwx.app/install | sh
srwx login --token "$SRWX_TOKEN"
# deploy the site — statics go to all 14 servers
srwx deploy ./dist --zone my-site
→ live at https://my-site.cdn.srwx.app
# after a release — clear the cache in 5 seconds
srwx purge --zone my-site --tag v2.4.0A quick look at what happens between a visitor and your file.
Each request lands on the nearest of 14 servers — 10–40 ms to the file instead of 150–300 ms across half the globe. For hot files, this is where most of the speedup comes from.
Hot files sit in edge RAM and are served in milliseconds; colder ones live on fast NVMe right next to it. A stale copy is served instantly while a fresh one is fetched from the origin in the background (stale-while-revalidate).
HTTP/3 over QUIC shrugs off packet loss on mobile networks. Brotli compresses text 15–20% tighter than gzip. Both are on by default — nothing to enable.
Start free — 5 GB storage and 50 GB monthly traffic. Pay only when you outgrow it.
No. You publish exactly the files your hosting already serves — nothing to rework. For a live site, one CNAME record is enough to point static paths at the CDN domain.
HTTPS everywhere, Let’s Encrypt certificates with auto-renewal. Management is token-based; files are public only within your zone. We don’t sell data and ship no third-party analytics.
Roll back to the previous version and purge — the rollback reaches all 14 servers within 5 seconds. A zone-wide purge is available too.
Storage is $0.015/GB per month, egress $0.01/GB, requests are free. Set a hard traffic cap in the dashboard if you want one: once it’s reached, serving stops — and so does the bill.